Skip to content

Conversation

@ghostrider77
Copy link

Combining data using server-side copy using client.compose_object("bucket_name", "object_name", sources) does not work. The reason is that the compose_object method iteratively calls the object_size property of each ComposeSource object and each of them recursively calls itself, resulting in a RecursionError.

balamurugana
balamurugana previously approved these changes Oct 27, 2025
@ghostrider77
Copy link
Author

Not sure if excluding pylint C0103 is the way to go, but I have no better idea.

Makefile Outdated
check: getdeps
@echo "Running checks"
@pylint --reports=no --score=no --disable=R0401,R0801 minio/*py minio/credentials tests/functional
@pylint --reports=no --score=no --disable=R0401,R0801,C0103 minio/*py minio/credentials tests/functional
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should not ignore the error.

Copy link
Author

@ghostrider77 ghostrider77 Oct 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How should we handle it then? Currently pylint throws this error on the master branch.

tests/functional/tests.py:56:0: C0103: Variable name "_CLIENT" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)

I could ignore this or the variable-rgx should be changed in the pylintrc file. I suppose this worked recently, otherwise it would not be on master. Maybe a pylint update causes it.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update: Pylint 3.3.9 works, 4.0.0 does not (released 12 Oct. 2025), so indeed a pylint update introduced this error.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refer #1521 how it is fixed

Copy link
Author

@ghostrider77 ghostrider77 Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so you already have a PR regarding this issue. Sorry, I have not checked it before. How should I proceed with this one?

  • Shall I wait for your PR to be merged so after the merge I can rebase my branch to master.
  • The other option is to convert those constants lowercase myself, basically repeating your work.
  • The third one is the one that I suggested in my latest version: keep their names as is, since module-level constants look better in all-caps, but let pylint ignore those lines.

@balamurugana
Copy link
Member

A better fix is #1524

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants